feat(lit-task-auto-top-up): Update worker to support 1-task-per-network on a single mongodb backend task tracking instance #5
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MaximusHaximus
requested review from
glitch003,
Ansonhkg,
joshLong145 and
DashKash54
Ansonhkg
approved these changes
Jul 2, 2024
|
|
||
| z.array(recipientDetailSchema).parse(recipientList); | ||
| z.array(recipientDetailSchema).parse(deprecatedHabaneroRecipientList); | ||
| z.array(recipientDetailSchema).parse(habanberoRecipientList); |
…to register network-specific daily task job name for Agenda - Now, we can run multiple worker instances (1 per network), but persist their jobs to a single backend Mongo instance without issue
…ipient list files in worker dir
…no-specific recipient list files in worker dir
…nts from deprecated generic json file
MaximusHaximus
force-pushed
the
network-specific-autotopup
branch
from
b64375c to
58861f6
Compare
|
Rebased and synced contents of Also bumped contracts-sdk to v6.1.0 to ensure we're using the latest changes re: setting |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With this PR, we can run multiple worker instances (1 per network), but persist their jobs to a single backend Mongo instance without issue.
recipient_list_manzano.jsonfile in theworkerdirectory, which our new manzano instance can be configured via env var to load.recipient_list.jsonfile in theworkerdirectory, which was habanero specific. The new file includeshabaneroin the same for consistency. Once this is merged and the existing worker is updated to reference the new filename withhabaneroin it, we can delete the existing generically namedrecipient_list.jsonfile.0x9f32f6555a117ac137775973C6856bC52c249C80in all 3 files -- this address is a 'stub' address that I use as a canary for the job/worker; it is a wallet that I created. It was set to mint every 5 days. I changed it to mint every 20 instead.